NTISthis.com

Evidence Guide: ICTPRG426 - Prepare software development review

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG426 - Prepare software development review

What evidence can you provide to prove your understanding of each of the following citeria?

Review the software standards

  1. Ensure that stakeholders have an understanding of organisational requirements
  2. Document the software standards, according to project standards
Ensure that stakeholders have an understanding of organisational requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the software standards, according to project standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the implementation standards

  1. Assign the software standards to functions, according to a detailed technical plan
  2. Take action to ensure that the communication and distribution strategies are clear, coherent, and meet the overall project plan requirements
  3. Monitor and report on the implementation of standards against the acceptance criteria and detailed technical specifications
Assign the software standards to functions, according to a detailed technical plan

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that the communication and distribution strategies are clear, coherent, and meet the overall project plan requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Monitor and report on the implementation of standards against the acceptance criteria and detailed technical specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the software metrics and milestones

  1. Define metrics related to the project milestones, timeframe, and cost considerations
  2. Develop a schedule of quality reviews
  3. Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements
  4. Determine a method to benchmark and scale achievement against stated stakeholder requirements and cost considerations
  5. Report metrics and milestones to stakeholders in a clear and coherent manner, and take action to ensure the written agreement
Define metrics related to the project milestones, timeframe, and cost considerations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a schedule of quality reviews

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine a method to benchmark and scale achievement against stated stakeholder requirements and cost considerations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Report metrics and milestones to stakeholders in a clear and coherent manner, and take action to ensure the written agreement

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Review the software standards

1.1 Ensure that stakeholders have an understanding of organisational requirements

1.2 Document the software standards, according to project standards

2. Review the implementation standards

2.1 Assign the software standards to functions, according to a detailed technical plan

2.2 Take action to ensure that the communication and distribution strategies are clear, coherent, and meet the overall project plan requirements

2.3 Monitor and report on the implementation of standards against the acceptance criteria and detailed technical specifications

3. Review the software metrics and milestones

3.1 Define metrics related to the project milestones, timeframe, and cost considerations

3.2 Develop a schedule of quality reviews

3.3 Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements

3.4 Determine a method to benchmark and scale achievement against stated stakeholder requirements and cost considerations

3.5 Report metrics and milestones to stakeholders in a clear and coherent manner, and take action to ensure the written agreement

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Review the software standards

1.1 Ensure that stakeholders have an understanding of organisational requirements

1.2 Document the software standards, according to project standards

2. Review the implementation standards

2.1 Assign the software standards to functions, according to a detailed technical plan

2.2 Take action to ensure that the communication and distribution strategies are clear, coherent, and meet the overall project plan requirements

2.3 Monitor and report on the implementation of standards against the acceptance criteria and detailed technical specifications

3. Review the software metrics and milestones

3.1 Define metrics related to the project milestones, timeframe, and cost considerations

3.2 Develop a schedule of quality reviews

3.3 Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements

3.4 Determine a method to benchmark and scale achievement against stated stakeholder requirements and cost considerations

3.5 Report metrics and milestones to stakeholders in a clear and coherent manner, and take action to ensure the written agreement

Evidence of the ability to:

review the software standards, including:

ensuring that stakeholders have an understanding of organisational requirements

documenting software standards according to project standards

review the implementation standards, including:

assigning software standards to functions, according to the technical plan

ensuring that communication and distribution strategies are clear, coherent, and meet requirements

monitoring and reporting on the implementation of standards

review software metrics and milestones, including:

defining metrics

developing a schedule of quality reviews

determining quality considerations by identifying the in-process measurement points

determining a method to benchmark and scale achievement

reporting the metrics and milestones to stakeholders

ensuring the written agreement is met.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

identify and explain current industry-accepted software configuration management processes

identify and explain quality assurance practices and standards

explain software metrics development

identify and describe the client business domain.